Added a comment
authorberyllium@5bc3c32eb8156390f96e363e4ba38976567425ec <beryllium@web>
Fri, 24 Jan 2025 08:04:27 +0000 (08:04 +0000)
committeradmin <admin@branchable.com>
Fri, 24 Jan 2025 08:04:27 +0000 (08:04 +0000)
doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment [new file with mode: 0644]

diff --git a/doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment b/doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment
new file mode 100644 (file)
index 0000000..a469b42
--- /dev/null
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="beryllium@5bc3c32eb8156390f96e363e4ba38976567425ec"
+ nickname="beryllium"
+ avatar="http://cdn.libravatar.org/avatar/62b67d68e918b381e7e9dd6a96c16137"
+ subject="comment 4"
+ date="2025-01-24T08:04:27Z"
+ content="""
+I don't know if this is expected behaviour, but for some files I imported from an importtree, when I use git-annex whereused --key with the correct key, nothing is shown unless I also add --historical
+
+And then I am shown the importtree branch information. It doesn't seem to make sense to me. The file is definitely present, and git-annex whereis confirms this, as does git-annex lock/unlock
+
+Willing to add more context if this is a little too vague
+
+Shaddy Baddah (beryllium at shaddybaddah dot name)
+
+"""]]